Immutables are great in a multi-threading environment because their contents can not be changed. Rather, an updated immutable is a new object which may share much of its content with earlier versions of same.
Immutables work great with actors, too. An actor would hold a reference to an immutable and provide unrestricted access to the current immutable. But updates to that reference would be performed only by the actor itself. Alternately, updates to the reference could be done under a lock. But then you are back to dealing with things like deadlocks.
Release 0.2.0 was the addition of versioned (mutable) map lists. Version 0.3.0 will be the addition of immutable versioned map lists. This is where the simplicity of the AA Trees used in release 0.2.0 pays off so nicely--it turns out that they are easy to transform int immutalbes.