"Cannot call write after a stream was destroyed" error when closing a TCP client

[sirockin]

When running TCP tests, the console shows the following error each time the client is destroyed:

Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed
    at doWrite (_stream_writable.js:411:19)
    at clearBuffer (_stream_writable.js:522:5)
    at Socket.Writable.uncork (_stream_writable.js:319:7)
    at uncork (C:\flow\third-party-repos\rx-mqtt\node_modules\mqtt-packet\writeToStream.js:75:10)
    at process.internalTickCallback (internal/process/next_tick.js:72:19)

Since this only appears once the client is destroyed, it shouldn't affect production although I would like to confirm it doesn't cause problems when reopening the client.