If you are in the Java world, this is where it pays to switch some classes to Groovy and use its @Delegate annotation. It's a compile-time AST transformation, such that straight-up Java code can take advantage, and it can inject the delegated interfaces into its parent class (so now the class can show up as implementing an interface for the dependency injection framework).
This can be introduced on an as-needed basis (make some files Groovy and the Java code can call them) and Groovy is essentially 95% compatible with identical Java code, so you can usually rename .java to .groovy and be good to go.
One of the authors of the @Delegate annotation (http://groovy.codehaus.org/gapi/groovy/lang/Delegate.html) went on to create Groovy++, a statically-typed booster for the dynamic Groovy Language, also working using an AST transformation. Just put @Typed in front of the your package, class, or method, and you'll see speed increases of 10 to 50 times over bare Groovy ( http://code.google.com/p/groovypptest/wiki/Performance ).
Unfortunately, the developers of Groovy aren't bundling it with their distro of Groovy. You'll need to go direct to http://code.google.com/p/groovypptest/downloads/list , or pick it up from http://groovy.codeplex.com .
Multiple inheritance is not just for specialization. See http://en.wikipedia.org/wiki/Mixin
On the other hand, reflection in the hands of over-eager users is already a nightmare... perhaps a huge speed bump in the way of full metaprogramming is a good thing for most projects.
As far as the actual application presented here.. it doesn't quite get you Scala's traits (no self-types) but it seems pretty close. Nice hack.