Hot Rod iteration state is kept around forever if IterationEnd is not invoked

The DefaultIterationManager keeps a map of iterationstate for each active client iteration. Unfortunately, if the client does invoke the end operation, these states can linger forever. We should:

• reap iterationstates when the channel that created them is closed
• reap iterationstates which have been inactive for a long time