amazon ec2 - Memory leak in Clojure web application -

I've created a web application in the closet, packed it into war, and posted it over Tomcat. . I hope this works, but when I turn off Tomcat, I see many exceptions like the following:

  SEVERE: Web application [] has a thread type Key is made with [Java. Lang.ThreadLocal] (value [java.lang.ThreadLocal@fc5408]) and a value of type [clojure.lang.LockingTransaction] (value [clojure.lang.LockingTransaction@12db7c]) but our application was stopped when failed to delete it Happened. This is very likely to create a memory leak. Marc 17, 2011 4:19:48 AM org.apache.catalina.loader.WebappClassLoader Spshtthretloklmap SEVERE: Web application [] made with a key Thredlokl type [tap] (value [ClojureklangkVar$l@llde9l4] ) And a type of type [clojure.lang.Var.Frame] (value [clojure.lang.Var$Frame@7c28c]) but the web application was stopped when it failed to remove. This is very likely to create a memory leak. Marc 17, 2011 4:19:48 AM org.apache.catalina.loader.WebappClassLoader Spshtthretloklmap SEVERE: Web application [] made with a key Thredlokl type [tap] (value [ClojureklangkVar$l@llde9l4] ) And a value of type [clojure.lang.Var.Frame] (value [clojure.lang.Var$Frame@17588d5]), but the web application was stopped when it failed to delete. This is very likely to create a memory leak.   
 I think there are some things that might be slightly ahead of the Java trash collector for some time. There is a subcontractor listener in my battle that starts some background threads but I do not see any reason that it should not only be done with grace (these are not all daemon threads)  
 Is there any better / Different way, should I use to start my threads, which is more tommy-friendly? Right now I'm just starting them by calling  (future (loop ... .) 
 
 
 apparently But in Tomcat - check the link.  
 I do not think this is actually a memory leak, it is more likely that Tomcat is excited to report the fact that some threads / threadlawl heaven ' 
 The alert is upset, but this is not really a fatal problem because all the threads are in the It will be released as soon as JVM will be stopped.  
 It's normal to start with your threads (future (loop ...), but you should ensure that they are real At the right time, you come out on the right time, meaning "Closing"? Check at each loop as atom might be. You will know that the warning removes it.