Er, don't? I mean, is that really a "bug"? (as far as GWT is concerned, it's not, it's by design)
handleCurrentHistory "updates" your *app* with the place corresponding to the *current* history token (which might not exist, it's then the "default place" you given when initializing the PlaceHistoryHandler), not the other way around.