turns out NSNumbers, among others, return true when asked if they respond to the mutableCopy method (as all NSObject subclasses should) but then throw an exception if you call that method on them... what a pain.