Place <-> Activity is *not* a 1:1.
Its' hard to tell from your example how it'd better be done, so I'll
try to guess.
Case 1: you don't really have those widgets, but rather "placeholders"
where you'll put them on place change (what I call "display regions").
In other words, this is the layout of your app, at the "top level" of
your widget hierarchy
In this case, you'll have 3 ActivityManager, one for each display
region, and each one with its ActivityMapper.
Case 2: the DockLayoutPanel is the "view" of an activity, and you want
to subdivide it into 3 "subactivities". In this case, your
"docklayoutpanel activity" should probably instantiate and manage the
lifecycle of the subactivities itself; or maybe you shouldn't even use
the Activity interface for your "sub parts". The idea anyway is that
your "docklayoutpanel activity" *knows* the "sub parts" and manages
them, whether they're "just widgets" (or components composed of a
presenter and a view).
Maybe this can help you:
http://tbroyer.posterous.com/gwt-21-activities-nesting-yagni
(it was written for 2.1 M3 and I haven't updated it yet, you'll find
the list of changes between M3 and RC1 at
http://tbroyer.posterous.com/gwt-21-places-activities-what-changed-between
)