200b is the utf-8 ZERO WIDTH SPACE character which is why it is essentially invisible in the database. All you need to do is decode the data when you extract it from the database and encode it when outputing it as HTML then this problem (and those caused by any other utf-8 characters in the data source) just vanishes.
I am using Class::DBIx
That may or may not be problematic but I would expect not. Check your database connection parameters as you may be able to specify automatic decoding on the fly. DBD::mysql has the mysql_enable_utf8mb4 option for this.
