If the livestream request data wasn't read in one go (i.e. EAGAIN was
hit), then it would recreate the context from scratch and attempt to
reread the whole request which would hang indefinitely and leak a jcl
context. This only seemed to present itself with hangle on with
localhost. Bug fixed.