Customer has raised 5032338 bug for this issue on application server codebase -7.0 UR4 .

7.0 UR4 uses JDK 1.4.2_04. Note that the same bug is applicable on 7.1 and 8.0 app servers which use JDK 1.4.2._05

When an application is deployed on the application server, one instance of EJBClassLoader is created. The EJBClassLoader instance should get derefernced from memory after undeployment of the application.

From OptimizeIt snapshot attached with bugtraq, it's clear that even though there are no incoming references, EJBClassLoader doesn't get removed from memory. In customer scenario, EJB is creating instances of 300 classes using new operator. Successive deploy/undeploy of the same application results in Permanent Generation running OutOfMemory.

Attached in the bugtraq is OptimizeIt snapshot that reveals EJBClassLoader instance having only valid Outgoing references.

The setup is available in machine : eas202
under /space/manisha/software/70ur4/

Command for deploying application :

/space/manisha/software/70ur4/bin/asadmin deploy --user admin --password adminadmin --port=4849 /home/mu125243/escalations/5032338/test/simple/stateless-simple.ear

Command for undeploying application :
/space/manisha/software/70ur4/bin/asadmin undeploy --user admin --password adminadmin --port=4849 stateless-simple

OptimizeIt is available at
/space/manisha/tools/OptimizeitSuite