@larkee pointed out an interesting observation in the Python library if we initialize the session pool with > 0 sessions in the context of ListDatabses and I think this might apply in Node.js as well.

1. When we call getDatabases, the GetDatabaseResponse translates the Database protos into Database objects.
2. Each Database object contains a SessionPool which is initialized in the constructor.

Is it an issue that we potentially create lots of sessions unnecessarily for all results of a ListDatabases call?

@olavloite assigning to you since you've looked at the pool implementation more recently.