"We view reducing memory usage as a blocking issue for final merger into the py3k branch. We seek guidance from the community on an acceptable level of increased memory usage."
To use a car analogy, PyPy is a race car that is not street legal, while Unladen Swallow is an European sports coupé that is slightly faster than the mild-mannered CPython sedan we all know and love while using somewhat more fuel.
As far as car analogies go, this one looks pretty good.
Their funding has ended, and I don't think they will manage to pony up another million+ in funding after 5 years. PyPy isn't compatible with C modules, and can be up to 5x as slow as Cpython (according to their own benchmarks). Making unladen-swallow the python standard will probably cause a brain-drain and make others hesitant to support PyPy.
On the other hand, Unladen Swallow is using LLVM, which may create the necessary tools for LLVM to be a suitable VM for dynamic languages (versus the JVM / CLR).
I consider this to be exciting news actually ... Python 3 doesn't offer me much, and I won't switch to a less supported Python version unless I have a bigger incentive (right now I'm happy with Python 2.6).
Maybe Unladen Swallow won't be able to achieve it's goals (5x faster), but if it's 3x faster with only a reasonable increase in memory consumption, than it's worth it.
PyPy is another interesting project that seems to be under active development ( nightly benchmarks against CPython http://buildbot.pypy.org/plotsummary.html ). I don't know how this decision on supporting Unladen Swallow will affect PyPy, but it would be a shame if it died as it has a lot of interesting ideas - - and I think it has a lot more potential than Unladen Swallow.