Memory leak occurs when:
- A client opens a secured JMXMP connection
- The client invokes an mbean operation which registers an other mbean
  provided by a jar file specified via an URL:
URLClassLoader cl = new URLClassLoader(new URL[] { url });
Thread.currentThread().setContextClassLoader(cl);
- The client gets an attribute value from the newly registered mbean
  and an access control subject object is created inside the getter:
        AccessControlContext acc = AccessController.getContext();
        Subject subject = Subject.getSubject(acc);

The all 3 conditions above are required to reproduce the memory leak but
memory is released when the connection is closed.

Note that this problem is likely to occur with multiple secured JMXMP
connection performing multiple operations on multiple mbeans.
###@###.### 10/22/04 13:02 GMT