CURATOR-157 Avoid stack traces on close

Avoid error-level stack traces closing PathChildrenCache followed by closing CuratorFramework

See details in jira: https://issues.apache.org/jira/browse/CURATOR-157
Can you explain why this works in a little bit more detail? My immediate intuition is that the compiler/JIT would optimize an empty synchronized block out of the code.