Fix thread leak on each call to NodeDiscovery.close().

Curator's PathChildrenCache leaks a thread unless you use the constructor that takes an ExecutorService explicitly and call shutdown() yourself.  See https://issues.apache.org/jira/browse/CURATOR-66.

As far as I can tell it looks safe to share the same thread/executor between NodeDiscovery and PathChildrenCache.