Add basic tests for classloader leaks following deployment, use and undeployment of various packages (wars, ejb jars and ears with and without scoped classloaders).

As part of deploy setup, test drivfer will deploy a sar with a service that deployments can use to register their classloader. Service will maintain a WeakReference to the classloader.

Test will deploy various packages and invoke operations on them (web requests and remote ejb invocations). Deployments will register their classloader, and during invocations will log using commons-logging (thus testing for leaks via commons-logging). Test driver will then undeploy the package check with the service to see if the classloader was released.

If JBoss Profiler is on the path and -agentlib:jbossAgent is passed to java, if the classloader is not released the service will generate and log a report tracing references to the classloader. This can be used to isolate the cause of the leak.