When 10 different app server processes create individual jdbc connections without using a connection pool there would be 10 sessions and not 1. If you are using a connection pool, then there would be the number of sessions specified in the connection pool configuration directives in the weblogic config file.

I have seen mixed results in this kind of an environment. If the application crashes and the developers are catching the exceptions and closing all connections you would be fine. But if the application server crashed, I had seen a lot of hung sessions.