Did you ever solve this problem. We are seeing this exact behavior in our application. WebSphere 6.1 cluster, Spring-based application... What is troublesome to us is that sometimes during testing the node that was restarted actually managed to corrupt the cache on the nodes that were not restarted. This of course stopped us from using this solution in production.