> It's not safe. You need to protect concurrent access to all objects  
> that are not specifically designed for thread-safety (like  
> SharedQueues):

Actually SharedQueues protect themselves, or at least the code appears intent
on doing so (it has its own 'accessProtect' Semaphore).

But yes, the standard "non-shared" classes like Set do not.