Within an application that we have that uses the RAM public api, we are encountering situations where we easily hit the per-user session limit (10) when attempting to share the use of an allocated RAMSession object. The pattern we have noticed is that within our multi-tabed web application, if we navigate to another tab within the application and then navigate back to the tab that we initiate RAM activity from, another server side session is being allocated. We have validated through tracing that we are not explicitly allocating another client side RAMSession object, but we are seeing the server side connections growing consistently. Is there something we can do to allow this session sharing ??