Hell, their AT&T contract was probably the only reason they got super up in arms about it anyhow.
The reason Apple closes the security loopholes is that they are security loopholes. It's not some sort of arms race. It's securing their platform.
Notice they have a pretty effective iBooks test for Jailbroken devices, but they don't deploy it widely, etc. I think they're at peace with the JB community as sort of a free research lab for them (hell, on device 3rd party apps came from the JB community first!) and use them to fix security holes in their platform as they are revealed.
Well, it's not that effective; it was worked around within days of showing up. Interestingly, to my knowledge, Google's similar check to prevent rooted devices playing movie rentals hasn't been worked around yet.
Defending against physical access-based exploits is likely always going to be ultimately futile, though.
1. They patch the bugs that, e.g., allow jailbreaking through a webpage or pdf (since those are genuine bugs could be used maliciously).
2. A device comes locked "out of the box", and can only run signed code (so that the vast majority of people need to use the App store).
3. They don't have to support jailbroken devices (so if you install an app on your jailbroken phone that doesn't play nice, it's not their problem).
Looking at sales figures for the app store and iTunes, would you honestly say that Apple's code-signing and other DRM techniques have "failed"?
Once the attacker (again, the owner of the phone who wants to jailbreak) has possession of the phone, he has complete control over it. I wonder if Apple has this internal posture that they should make appearances of caring about jailbreaking (for the benefit of the carriers and their contracts) but actually it's not such a big deal.