Red5 - Keeping transient shared objects alive on server

Question

I create a transient (non-persistent) remote shared object using ApplicationAdapter.createSharedObject(). Then a client connects to the application. The client then connects to the shared object. But when the client leaves the application and connects again, the shared object is no more there. The properties set by the client in their previous session are lost and so is the shared object. Is there a way to keep the shared object alive even when there are no clients connected to it? I don't want to use persistent shared objects because there are going to be thousands of them and each persistent shared object creates a new file on server, which has to be slower than non-persistent remote shared objects.