Braddock's Crab guy is awesome. Interestingly your example came in just a few 1000 polygons under the limit. LOL
I did see that the limit only applies to STL files, but then I have to ask WHY? Seriously. What is the point? That just seems so arbitrary and frankly, kind of stupid, for what is otherwise an amazing program. There are already enough distinctions and limitations between R7 and Core that the polygon limit on STL files just seems so... after the fact? Random? Silly? Easily dodged, as you have shown, to the point of it just being a pain in the a&& to the end-user?
Therein, I think lies my only real gripe, they went out of their way, when they did not have to, to create an intentional obstacle for the user that does not need to be there. That's not bad code, that's just bad practice. That's the kind of shady BS we saw in the 80s. Can I work around it? Yes. Should I have to, is it functionally required? No.
So straight shooting, no bullshit, I kind of have issues paying money for software that includes completely unnecessary intentionally placed obstacles. Could I work around it? Sure. I could just pirate it too and not worry about it at all...
Believe me, I have watched ZBrush demos live, watched tons of videos, even bought a book. It is software that I really want to get into and learn, but I do not support arbitrary paywalls and I vote with my $.