It looks like the application classloader is being used to load class after it's destroyed.
There are two parts to the stack trace. The first part shows you a snapshot when the classloader was destroyed which is at "undeploy" time. This is expected behavior as we do intend to destroy classloader after undeploying an application.
The second part shows where the previously destroyed classloader is being used again to load class. This is the problem we need to figure out, why that classloader was used again to load classes. There could be various reasons for this. This is one case:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=3229
As the stack trace is from webservices code, webservices team should probably be able to help further.
[Message sent by forum member 'hzhang_jn' (hzhang_jn)]
http://forums.java.net/jive/thread.jspa?messageID=246346