[GSS](7.3.z) Caching of managed beans in WebInjectionContainer can cause memory leaks in distributed JSF applications following session timeout

Steps to reproduce of scaling up scenario with the attached jsf-managedbean-test.zip in the local environment: 1. Extract jsf-managedbean-test.zip and build jsf-test.war $ unzip jsf-managedbean-test.zip $ cd jsf-managedbean-test/ $ mvn clean package 2. Deploy the generated jsf-test.war to all nodes of your cluster 3. Start node1 4. Send many requests to node1 and create new sessions ab -n 10000 -c 200 http: //node1:8080/jsf-test/index.xhtml 5. Start node2 and form a cluster 6. Wait 1 minute for session timeout 7. Check heap dump of node1 jmap -dump:live,format=b,file=/tmp/headump.hprof <JAVA_PID> or you can do a quick check with "jmap -histo:live" to count the number of remaining JSF Managed Bean (com.example.beans.*ScopedBean) jmap -histo:live <JAVA_PID> | grep com.example.beans Actual Result: Some JSF Managed Bean (half = around 5000 instances) remains in heap even after session timeout. Expected Result: All JSF Managed Bean should be GCed after session timeout.