Don't think so ; CMN_SESSIONS holds some session detail but I think things are only really persisted to the database in order to handle handing off one session to a different node when the "application" needs to, and all that would be held "in memory" in the application layer.
The access log files on the relevant nodes would tell you though ; you can see session ids in those - so you could (I guess) set up some automatic parsing of those to find the session details perhaps?
Also the action:security.caches&selected=caches hidden page shows the server name in the window title (only have access to that if an admin user) ; you perhaps might be able to debug that page in order to work out if you can get the info some other way.