I don't personally prefer to subscribe to the "it's the user's fault" school of UI design. While sometimes a problem is the user's fault, it's not an auspicious starting position.
If a UI design presents a slot or button or knob to an inexperienced user, then you should expect it's going to occasionally going to get poked at. Humans are an inquisitive lot, after all.
And if some unique and irrevocable things happen that's also specific to your device, then you're going to lead an inquisitive user to have a problem. Particularly if the slot is commonly used for transferring data in and out of other similar devices.
Most folks don't encounter and don't poke at RAID disk arrays. Most folks do shuffle files and pictures in and out of handhelds and laptops and cameras via SD. If you're aiming for the former audience and your product happens to be bought in droves by the latter (and as is increasingly arising with SOHO and consumer-facing RAID devices, for that matter), you've missed your target product audience, and you're going to have product acceptance problems.
Worse for WP7, this particular case likely arises among the more inquisitive members of your target audience, and this is likely also the same group that can be your early adopters and your best proponents.