Description of problem:
If an ear does not have its own LogContext created, but a subdeployment in it does, the subdeployment never has its LogContext cleaned up upon undeploy, leading to PermGen leaks.
Steps to Reproduce:
1. Set trace logging for 'org.jboss.as.logging' to easily see log context adds and removals.
2. Deploy attached ear
3. undeploy ear
4. Note the log context is not removed
Log context is not removed for subdeployments
Log context is removed for subdeployments
Verified with 6.4.9.CP.CR1
Jiri Pallich <email@example.com> updated the status of jira JBEAP-4101 to Closed
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.