That issue is not a jboss issue. Its broken code hanging onto destroyed class loaders as stated in the case.
As a workaround I am packaging the axis jar with my ejb archive. This appears to work.
If this issue is about an Apache Axis WS client it should be discussed through whatever Apache offers as a support channel - not here. Axis is not supported in JBoss. See the FAQ page for details
J2EE-1.4 compliant WS clients do not have this issue.