rushead,
Did you ever find out if this behavior is expected? I've run into the same issue, and I don't want to pollute my ExceptionMappers with code that really only belongs in a PostProcessInterceptor, but, like you, I don't really see any other option...