title: can websocket exhaust webserver's connection pool
body: <p>I have seen a lot of people have written Ajax(polling) vs websocket. I have not seen anyone mentioned below disadvantage of websocket.</p>
  
  <p>As we know for each http request web-server needs connection.There are maximum number of concurrent connections web-server can support,beyond that if a request comes,request will have to wait till any connection is fee.  </p>
  
  <p>I case of simple http request(poll based),when a request is served by server connection is put in pool and that connection can be used for next request,so it is very unlikely in simple http request,a request will be waiting for a connection.  </p>
  
  <p>But in websocket connection is never put back in pool of webserver,so it is going to very frequent that next request will have to keep waiting for ever for connection. </p>
  
  <p>So,I want to know,Am i thinking correctly or missing something. I am correct,how this is solved?does this issue ever occur?</p>