ClassLoader leak when using the reports and then hot-redeploy with Tomcat 7.0.42 or later about javamelody HOT 3 CLOSED

I have reproduced the issue.
There is indeed a classloader leak when:
- using hot-redeploy
- and using Tomcat 7.0.42 or later
- and the monitoring graphs have been displayed before redeploying.
Only one classloader is leaking, not the ones of every redeploy.

It happens because javamelody uses javax.imageio to display the graphs and 
javax.imageio has a classloader leak inside 
sun.awt.AppContext.contextClassLoader.
Before Tomcat 7.0.42, we were automatically protected of the javax.imageio / 
classloader leak by the JreMemoryLeakPreventionListener of Tomcat.
But since Tomcat 7.0.42, the AppContext protection is unfortunately disabled by 
default in JreMemoryLeakPreventionListener of Tomcat and we are no longer 
protected against the AppContext leak.

This is now fixed in trunk by adding a new protection (revision 4070) and ready 
for the next release (1.56).
Thanks for the issue.

Issue 369 has been merged into this issue.