J, as you've seen in my QA diagram, that's what we're doing (BAS + CoreBES + SQL on three separate levels). If and when we have the need to break one of the services out, we will do so. However, as it stands with BES, I have an OOBE of 350MB total RAM usage (OS + BES), so I don't think this is going to be much different than BES 4.x on resources.
I can definitely see how the distributed model would help RH in his environment. He had also mentioned the monthly PDF patches would be easier to install with a distributed Attachment Service, which I completely agree with (except the fact that we've simply given up on applying these patches in our environment, as the potential for risk is slim given that these are processed 4 levels deep in the environment). I do use this as a tongue-and-cheek example of distributed components whenever I'm in a RIM training class, though