ServerStreamPool.ConnectionLoop prevents shutdown

[philippseith]

I recently forgot to dispose a NamedPipeServer in my applications shutdown logic. Because the ServerStreamPool.ConnectionLoop is not started as a background thread, the application did not end.
I understand that it is good practice to dispose disposable objects on shutdown, but I wonder if this is really necessary in this case. Is there a reason why ServerStreamPool.ConnectionLoop is not a background thread?

See

grpc-dotnet-namedpipes/GrpcDotNetNamedPipes/Internal/ServerStreamPool.cs

Line 102 in da307b5

var thread = new Thread(ConnectionLoop);