Use 'break' instead of 'return' to abort the slurper thread.

With 'return' we wouldn't get the final 'info' message that the slurper has stopped,
and what the river status is now.
Make the 'tailerThreads' member final

'tailerThreads' is never changed after construction, although the content may change when the river
is started or stopped. This is however not covered by the 'volatile' keyword, and there is really no
need to allow concurrent modifications of the content (at this point).
Merge pull request #425 from Collaborne/tailer-threads-final

Make the 'tailerThreads' member final
Merge pull request #424 from Collaborne/slurper-break

Use 'break' instead of 'return' to abort the slurper thread.