Disconnect overtakes final message

When I send a message and disconnect a client immediately afterwards (in the same tick) it seems like this last message is being dropped. I was wondering if the framework shouldn't make sure that no messages are lost, meaning that message and disconnect are processed in the appropriate order.

This is a simple code example in C#:

var message = new FinalMessage();
client.Send(message.Serialize());
client.Disconnect();

The FinalMessage will not arrive at the host.

Start by tracing the C# Send and Disconnect calls shown in the issue and how they are handled when invoked in the same tick. Reproduce the sequence with FinalMessage and verify whether the host receives it before disconnect processing; done means the final message is not dropped and ordering is preserved.