Is a c# concurrency bag safe for websockets considering it maintains closed sockets
<p>Most tutorials for c# asp.net websocket implementation suggest using a concurrency bag for storing the sockets. I've noticed however that the bag holds onto all the abandoned and closed web sockets. Won't this just grow and grow until it is taking up too much resources?</p>

<p>Here is one tutorial among others which suggest storing the socket in a concurrency bag. <a href="https://medium.com/@turowicz/websockets-in-asp-net-5-6094319a15a2#.vdoh0cute" rel="nofollow">https://medium.com/@turowicz/websockets-in-asp-net-5-6094319a15a2#.vdoh0cute</a></p>

<p>Does anyone know if my concerns are justified in an ever increasing bag of closed sockets? Any other approaches out there that you can suggest or link to?</p>