Oh, no, it shouldn't scare you. It's given to ensure you know the program may glitch out, and you should at least have backups, but probably shouldn't let the program have control of your life savings if you're worried about a .00000000000001% chance of something catastrophic happening. It's possible there's an unknown bug which could cause this.
Armory introduced/introduces many new client-side features over Core (on top of some re-writing/changes with Armoryd). Gavin receives some praise from the community, actually, for being so conservative and not introducing all sorts of new features to Core, and this is because when you introduce more moving parts, you increase the chance for bugs, including potentially-catastrophic bugs. However, it sacrifices many innovative security, usability, and convenience features Armory and other clients have. -So you have to weigh this when making a decision. Long-term, what you really want, especially when dealing with something like Bitcoin clients where it's handling your money, is for a slow release schedule with many, many testers using dev/testing branches before they're pushed.
In game development (where users aren't putting up thousands or more dollars at stake), it's not uncommon for even small-medium sized dev teams (or their publishers) to require, say, 100-500 early testers to put in at least ~5 hours on a dev/testing branch (or complete the game) and complete some kind of survey before they push the update as a stable patch to everyone. I'm not sure even Core matches that amount of QA, though QA in a Bitcoin client is obviously monumentally more important. In development, it's often not that developers are just slow to put in all these cool new, features, but that they're waiting on testers and their surveys, then fixing anything critical which pops up, then requiring the same survey, possibly redoing that process yet again, and only THEN pushing the update out for auto-update applications (if non-critical bugs are identified by testers but where devs feel they don't outweigh the positives, you'll often see that in the "Known Issues" section of the changelog for games). Gavin has that kind of conservative mentality, I think, where relatively little is introduced, and it goes through a somewhat rigorous testing process (I imagine much less rigorous and without nearly as many testers as he'd like) to ensure to a high degree that everything's alright with it before pushing it as a stable update. In the same regard, BIPs take FOREVER.... it's like a budget bill in the US.
That's not to say Alan doesn't have the same kind of mentality, but it's pretty obvious Armory's introducing features at a much faster rate than Core while having a smaller team (both dev and testing), for better or worse (I'd argue for better, but I'm a bit impatient). I don't think Alan & team does too much with the daemon, either, which is probably where your critical bugs would appear... but I'm already way out of my knowledge zone.