Luis, I noticed today that the old bean factory used to test for the existence of an init() method before calling it. WireBox attempts to call the constructor regardless of whether or not it exists unless a mapping with noInit() is specified. The behavior came up when I switched over to WireBox and realized a had a couple models floating around that I had never added an init() method to. (and they errored)
Anyway, WireBox is doing exactly what the docs say it should do, this E-mail was just to ensure that was an intended and desired reversal of the default behavior.