I'm not sure what specifically you are referring to, but as someone who does an extensive amount of CQ development with Maven, I can tell you that I have not run into any issues with Maven 3. If you can provide more specifics on what you "heard", I may be able to provide more context.
Apparently a plugin was used that does some specialized CQ deployment. It's possible the issues show up with that.
Ironically, the two people who recommended we specify Maven 2.2.1 are CQ specialist contractors who are no longer with the team.
In fact, one of those CQ specialists was named "Justin".