Yes, they do.
You're right, generally, the size of UTXO Set has been growing over the years. E.g. in May 2014 it was 11 million, in May 2015 it was 19 million, May 2016 it was 38 million, in May 2017 it was 51 million.
Now, there are actually fewer than 50 million UTXO. How did that happen? As you noticed, spending a lot of UTXO in a single transaction is much more expensive. When the Bitcoin network was congested last winter, many Bitcoin users (especially businesses) were paying exorbitant transaction fees, because their funds were split into so many small UTXOs. At peak price and congestion spending a single UTXO could easily cost more than $10. Especially when multiple UTXO were needed to build a transaction, they were painfully expensive. Naturally, many users aimed to create the smallest possible transactions and skipped consolidations altogether, which caused the UTXO Set to grow rapidly in the congested phase.
Let's look at the UTXO Set size in the past year:
Even though more efficient usage patterns had been suggested well before the winter (e.g. Harding's excellent article on Batching in August 2017). Adoption of batching and frequent consolidations only peaked after the crisis. It seems that the price rally in combination with the severe congestion made Bitcoin users more aware of their wallet's UTXO pool compositions. From January to March we see an extreme regression of the UTXO Set size from more than 64 million to 51 million UTXO. When you look up blocks from then, you'll find many transactions that spent numerous UTXOs to single outputs. These transactions often paid very low fees, queuing in the mempool until fee rates dropped low enough for them to be included.
These consolidation transactions only had the express purpose of condensing funds into fewer UTXO at the lowest possible cost.
See this example from mid April:
As the transactions paying very low fees get included in blocks, the size in the UTXO set drops.
Since then, we've also seen a significant increase in use of batching, which tackles the UTXO Set growth from another angle: batching reduces the number of change outputs that get produced. When sending twenty payments in twenty different transactions, chances are that you will be creating 20 change outputs. When you send twenty payments in a single transaction, you'll only create a single change output. Heavy use of batching can therefore cut the UTXO creation per payment almost in half.