Perhaps. It may well be (and I'm probably ranting about issues I don't know enough about) that the orginal source section is there as intrinsic functionality for running the bytecode. In any case, I don't think the Parrot/Ponie people should go out of their way to appease the "hide our code" group.
"There is no shame in being self-taught, only in not trying to learn in the first place." -- Atrus, Myst: The Book of D'ni.
We aren't going out of our way -- I don't much care whether you can or can't hide your source. Not my problem. I'd expect that even mildly optimized code will be fairly difficult to turn back to source, and we're certainly going to give the capability to strip out the source metadata from the bytecode (mostly for space reasons, but we can't force all the compilers to emit sane source metadata so we have to be able to run without it) so folks'll be getting at least some 'hidden source' capabilities.
If this offends someone's sensibilities, I fully expect we'll have at least a primitive decompiler relatively quickly. :) And parrot'll ship with a working disassembler if you don't mind assembly. (Whether that helps depends on what we do, if anything, for signed or ECC'd bytecode)