Heya Ekki,
Glad you found a solution. This problem is caused due to a design choice we made in version 2.0.0 which caused a new connection to incorporate the provided ConnectionInfo parameter. This means connection specific information is added to the ConnectionInfo which obviously causes issues if two connections share the connectionInfo. I will discuss possible resolutions with our other developers.
Kind regards,
Marc