Closing durable object's websocket results in exception

Every time I have the client close a websocket connection, it results in an error exception. The exception array is empty. However I have tried just a websocket on a worker and it results in an exception as well but it does state the exception of “Network connection lost”. So I’m assuming that’s what the exception is in the durable object as well. If I don’t close the websocket on the durable object, the client hangs on disconnecting for a minute before erroring out with no close frame received. If I do close the websocket connection upon a close message, it properly disconnects the client but I get exception errors in my worker’s metrics and logs. I’m not sure if I’m writing the code correctly, I looked at all the examples I could find in case I am doing something wrong. Anybody else experience this and is this just a bug in the platform?