Session must always be closed

I added a destructor but no idea how to test it, since we ran into this issue only if we run into a fatal error earlier. I'm also wondering if adding this could mean that we can remove some of the disconnect() calls that are in the API class.

Maybe we could remove some calls, but it doesn't hurt to keep them, disconnect() checks if there is an open connection. If you want to make sure it works and is called, you could set a breakpoing in __destruct() (and optionally remove the explicit disconnect) when doing any operation, you should see it go in there then at some point.

Merged.

Automatically closed - issue fixed for 2 weeks with no activity.