I'm going to make a wild guess here and assume you're using Maven to launch Wildfly for your project, after having done the same for other projects.
What's probably happening is that Maven is simply launching a master copy of Wildfly and whatever WARs/EARS have been deployed to that Wildfly are launched.
In other words, Wildfly is, like any other JEE
webapp server NOT a place you simply dump files, it's a service for running webapps (WARs and EARs). And Maven is simply deploying your latest build and launching Wildfly. Unless Maven also undeploys
webapps, they're there until some external force removes them. That includes any situations where Maven intended to undeploy but something terminated the Maven process before it could.
To get rid of the old crud, try launching Wildfly without Maven and see if its "control panel" isn't listing all those apps. If so, undeploy/remove them from Wildfly.
There may also be an undeploy Maven goal, but since I don't launch webapp servers from Maven (I usually launch stand-alone or from an IDE
) I don't know for certain.