Fix SessionPool OOM problem when the number of devices and sessions is large

In current code of sessionPool, each session has an independent ConcurrentHashMap to record the device -> endPoint informations. 

However, when SessionPool has large number of session and each session need to insert a large number of devices, the ConcurrentHashMaps will take a lot of memory, which may lead to OOM.