I am having a similar problem with deploying a ear that contains 1 ejb-jar and 2 wars. Both wars have the 'java2ClassLoadingCompliance' atty set to false in there jboss-web.xml file.
Upon deployment, the first war to register itself works great. The second app however does not work correctly as it is accessing the first deployed web apps property files.
I have tried to isolate the wars loader repositories by specifying a unique <loader-repository>domain:loader=something.war</loader-repository> in both wars jboss-web.xml files. When I specify a loader repository I get a WARN message in the server.log for each web app that is as follows:
2004-04-13 01:36:16,912 WARN [org.jboss.deployment.DeploymentInfo] Only the root deployment can set the loader repository, ingoring config=LoaderRepositoryConfig(repositoryName: test.com@:loader=test-web.war, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: null, repositoryConfig: null)
I have read the forums in search of a solution without much luck. Any help would be appreciated.