Abort service does not work with outgoing TCP connection

When using the Abort service to abandon an outgoing TCP connection (client usecase), the connection will be gracefully shutdown as if Close service had been used. A  FIN/ACK sequence is seen on the network instead of RST. Also the Abort service confirmation takes a long time like Close service confirmation. The problem does not occur when using Abort service with an incomming TCP connection (server usecase)

It is expected, that when Abort service is used to abandon a connection, a RST is sent to the peer and the resources are immediately released