Fix leak of -1 sessions on tests using CoreFeature

Tests using CoreFeature sometimes show the following error log:

ERROR [CoreFeature] There are 0 open session(s) at tear down; it seems the test leaked -1 session(s).

This is due to the fact that there are already some open sessions at startup.

The message should be made clearer, and the test should ensure there are no open session at startup.