Hrm, I guess that isn't as interesting as it just shows Tomcat's shutdown thread saving the session. You are right, the bigger question is how CacheStaticMethodMatcherPointcut ended up in your servlet session.
CacheStaticMethodMatcherPointcut is auto-registered as a bean in the Spring application context when the <ehcache:annotation-driven> element is present. The only other piece of our code that references it is the DefaultBeanFactoryPointcutAdvisor which returns the pointcut to use for evaluating which bean methods should have caching advice applied.
Are you referencing your spring app-context from an object stored in the session?
-Eric