This is a sub-issue of issue 2060. See that issue for more information.
After the SAS timers expire on the remaining 2 SASes, each of which has an SS
child, only one of these SAS-SS pairs is actually removed from the active cache.
One SAS and one SS remain hanging. After 75 minutes, the active objects listed
still contains these objects, even though both are invalid according to the same
Active Objects in Application: SIP:cluster1:com.sun.appserv:server:/ZAsyncProxy
SAS: 0,36,daac04daae2e897d403ab10b85dde37c9aa6snasim ref:
SS: daace15a9e409bea4192bc4d482c2fcd3a7d##126.96.36.199 at: 2009-12-08
(In the log file attached to issue 2060 does not show the 75 minute wait, but
trust me they remain in the cache