Transaction recasters are a good thing. They make plainly visible an aspect of the protocol that was thus far obscure, and highlight implementations that don't cope with it properly. As long as transactions remain malleable, transaction recasting should be a permanent feature of the network, done by default for all transactions, so that people don't write software that relies on unconfirmed transaction IDs.

Apparently, even the reference client is affected, to the extent that it allows spending of a previous transaction's change based on an unconfirmed transaction ID. This has to be fixed, or else the reference client does not handle malleable transactions as properly as the developers supposed in their replies to MtGox.