What steps will reproduce the problem? 1. Whe application using LambdaJ is redeployed, Tomcat writes to the log information about probable memory leak

What version of the product are you using? On what operating system? 2.3.3 and 2.4

Please provide any additional information below.

17.7.2012 16:03:28 org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks SEVERE: The web application [/XXX] created a ThreadLocal with key of type [ch.lambdaj.function.argument.ArgumentsFactory$1] (value [ch.lambdaj.function.argument.ArgumentsFactory$1@127fbd60]) and a value of type [ch.lambdaj.function.argument.ArgumentsFactory.LimitedValuesArgumentHolder] (value [ch.lambdaj.function.argument.ArgumentsFactory$LimitedValuesArgumentHolder@69f31d]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

Created pull request at GitHub https://github.com/mariofusco/lambdaj/pull/1

I think is very important to fix.

I am also getting the same message on GlassFish 4.0 and 3.1.2. There is a significant memory leak and after about 2 days running, glassfish uses more than 95% of CUP usage and crashes. Please address this issue. Thanks in advance.