In WildFly it is considerred intended behaviour that test code gets called with the TCCL set to the test deployment. IMHO this shadows potential problems when the functionality under test is not called from an ARQ test case (i.e. from an normal javaee endpoint)

For Camel integration this behaviour is not acceptable.

CrossLink: https://github.com/wildfly-extras/wildfly-camel/issues/340