Details of the scenario are in the parent issue for this bug: http://java.net/jira/browse/GLASSFISH-15423
The re-run of this RichAccess 24x7 scenario with build 37 shows slow but evident memory growth. One of the instance's (instance101) jmap (-histo:live) logs were taken every 20 minutes. Three of those are attached here and so is the CPU/Mem plot. The jmap -dump and the -histo:lie logs will be sent directly to Mahesh.
The jmap -histo:live log files from the instance indicate a slow rise in number/size the following data structures:
The observed memory growth is perhaps slow due to the low number of simultaneous users (100 per instance).