The .NET client doesn't trigger the error handler when sending over WebSockets during a reconnect. Instead it just returns an empty task.

I'm thinking we should change the .NET client as well in order to make this behavior more consistent.