No, that's usually the way I do it to apply transactionality to all my beans. There are performance implications with proxying methods, particularly around the initial load (because of the filesystem/compiler churn), but it's snappy enough at runtime.

The particular case that drove this class was an app where every method is proxied for transactionality, but a single method on a single bean needed to be non-transactional (it manages it's transactions manually with CFTRANSACTION and a single method invocation encapsulates several distinct transactions.