Wave Mysteries

I am totally mystified by Wave's CPU and memory usage. Load a large (over 150 blips) but simple (text only) wave and watch your browser's memory usage soar to 500MB. On my older 2GHz Athlon 64, CPU usage hits 98%! What on earth is Wave doing that needs that much resources just to display lots of text? Since Wave is still alpha software, one hopes that those resource demands will improve, but even a 50% improvement would still be outrageously high.