I'm not sure if that's possible.
The usual suspects are logging, hibernate, JAXP (XML parsers) and apache CXF classes. Are you having trouble with any of these?
Right now logging is our main concern. Docs on EAP 6 do not mention any implicit dependency on them (slf4j, log4j, etc), while docs on AS 7.1 do. Having this information "per deployment" would help making sense of it all.
From what I have observed, JBossAS, EAP and WildFly all provide implicit implementations of the "common" logging APIs, the idea being that the application server controls logging. Other vendors do this explicitly for java.util logging, but nothing else.
How you deal with this depends upon what you're trying to achieve. Personally, I've always gone with the "application server controls logging" model, but I know that many people don't like that.