Queries continue streaming rows even after TCP connection timeout

When there is a long running incoming query (such as one with a very high "limit" parameter), the query continues streaming results even after the front-end times out. On the client side, it appears as thought the query has timed out, however, view-engine continues to use up CPU and memory servicing queries. A fix needs to be put in place to properly terminate the sub-processes spawned in order to service the queries.