Hi @andrey,
Thanks for reporting this! It looks like there were some HTTP requests being made (mainly due to push notifications but also in some other places) that were the cause of this due to some non-closed responses.
I've submitted a pull request here to get the issue fixed which should release with v3.3.