It was noticed during start-up of a very small client UI application on
Solaris SPARC that SoftReferences that had just been created were cleared
as soon as a GC came along. This is because:

"The client JVM prefers to flush SoftReferences rather than
growing the heap; the server JVM prefers growing the heap to
flushing SoftReferences"

This RFE requests implementation in the client VM of a heuristic that
below some (TBD) heap size the heap grow rather than clear SoftReferences
Otherwise caches cleared during GUI start-up will just slow down start-up
as such work will likely need to be re-done before very long at all.