Jetty strives very hard to stop classloader pollution between contexts. But then applications can often work very hard to defeat that effort... eg if they pass an instance of an object via attributes of a cross context dispatch. Other issues can be caused if classes are put on the server path and exposed to individual contexts.
So Jetty itself should definitely not reuse classloaders. We go to great efforts to flush out all loaded objects when a context is stopped, just to stop the memory leak issues. We definitely don't deliberately pass objects or loaders between contexts.
So to work out what is going on, we need a better picture of your classloaders, both for the server and all the contexts (a jetty server dump would help with that). But we also need to know if there is any cross context dispatching going on, or any other communication between contexts?
regards
