mis-linked frameworks result when including iLifeSupport.mpkg in build

I recently built an InstaDMG deployment based on 10.5.2 build 9C2028 (ships with the latest multi-touch MBPs) and it resulted in some mis-linked frameworks. I only discovered this when the Desktop & Screen Savers pref pane refused to open and the Console pointed to the ImageKit.framework not being loaded. Searching through the list of packages I included in the build singled out [b]iLifeSupport.mpkg[/b] (v8.2) as the one that touches these frameworks. The undesirable effect, specifically, was that in [b]/System/Library/PrivateFrameworks/GraphicsAppSupport.framework/Versions/A/Frameworks[/b], both the [b]ImageKit.framework[/b] and [b]QuartzComposer.framework[/b] links were pointing to [b]/Volumes/InstaDMG/...[/b] rather than the root volume. I was able to repair the broken links by manually applying iLifeSupport.mpkg.