CacheAsBitmapMatrix bug?

Hi.

I've been testing some features of Air for android using the latest version of flash CS5 / AIR for android ext and found this unexpected behavior when testing on a device.

I have a small testing project, this first two rows of graphics (the cats and the rats) are movie clips containing simple vector graphics (no filters).

The difference between them:

Cats:

Left: a movieclip, on stage (using the ide) with a scale (x/y) of 150% + caching by code.

Middle: same as the left cat but without caching.

Right: a "prescaled" movieclip on stage (using the ide) with a scale (x/y) of 100% + caching by code (I simply scaled the elements within the mc).

Rats:

Left/Middle: same as left and middle cats, but with a scale of 230% [both x and y].

Right:  a scaled movieclip inside an empty container mc, created by code. inner mc scale = 230%, outer mc scale = 100%. caching of outer mc.

Note: by "caching" I mean using both cacheAsBitmap = true AND CacheAsBitmapMatrix = new Matrix();

On the computer, using the flash ide/AIR debug  launcher:

no problems (but it doesn't support CacheAsBitmapMatrix so it's not a fair test).

On the device (samsung galaxy s, 2.2, latest air runtime):

when building for CPU, cache as bitmap matrix results with pixilated graphics for mc that are scaled, even when the caching is done on the object after it is scaled (the texture is always created from the 100% mc graphics).

when building for GPU, cache as bitmap matrix results with distorted graphics (it seems that the gpu texture is not in the right size or something).

But, if I stop using CacheAsBitmapMatrix and use only cacheAsBitmap, all of this graphic weirdness disappears...

Any thoughts?